Conversation
|
@tnull for review. |
There was a problem hiding this comment.
Did a first pass, excuse the delay.
What is our current thinking about landing this in conjuction with follow-ups? Do we want to land this and hide the code behind a cfg until it's ready to be published, or should we keep this PR open until all follow-ups are ready? As the changes shouldn't overlap too much with the rest of the codebase, we could also do a feature-branch for this and merge it into main once it's ready?
|
Regarding landing this PR or related PR's to VSS. I do want to merge them independently into main so that we close on things. Or expose public interface only once we are ready. Let me know if that works. |
Yeah, that generally works for me, but let's feature-gate it (behind |
b4c76a6 to
d10bf2e
Compare
|
Rebased to #151 |
|
@tnull Can i get review on this ? |
Sure, could you rebase now that I landed the 0.0.117 PR? |
|
Rebased after #151 landed |
|
Resolved all comments, ready for review again. |
jkczyz
left a comment
There was a problem hiding this comment.
Largely looks good. Don't have any other comments besides these.
|
Failing test is fixed in #184. |
jkczyz
left a comment
There was a problem hiding this comment.
I'm good with squashing the fixups and rebasing.
tnull
left a comment
There was a problem hiding this comment.
LGTM, should be ready to go, just two really minor nits.
A KVStore implementation that writes to and reads from a [VSS](https://github.com/lightningdevkit/vss-server/blob/main/README.md) backend.
Note:
This PR does not add full support of VSS, there will be additional PR's for some of the changes.
Currently it introduces only VssKVStore which is major chunk of code.
We will call it full support only once we make changes to public api for ldk-node.
Note on testing: